Historic datasets (from 2014 onwards) for the .nl TLD. Datasets are available in JSON format.
Datasets cover information about:
Historical DNS database. Access can be requested for academic use.
Activly queries many DNS records, e.g., .com zone.
It can contain information not in DNSDB, if the information was never seen by a resolver.
It does not contain all informatin, as some domains may be unknown to the project and thus cannot be crawled.
It uses popular zones, domain lists (e.g., Alexa, blacklists) and other domain feeds.
They normally maintain a rolling 14-day window.
Copy files (for date 2017-10-05) (ddos@gladbeck):
sftp -B1024000 -C -rp "activedns@kokino.gtisc.gatech.edu:active-dns/20171005/" .
The data is encocded in AVRO format, which can also be parsed as JSONL. Python has a AVRO library. AVRO schema:
{
"namespace": "astrolavos.avro",
"type": "record",
"name": "ActiveDns",
"fields": [
{"name": "date", "type": "string"},
{"name": "qname", "type": "string"},
{"name": "qtype", "type": "int"},
{"name": "rdata", "type": ["string", "null"]},
{"name": "ttl", "type": ["int", "null"]},
{"name": "authority_ips", "type": "string"},
{"name": "count", "type": "long"},
{"name": "hours", "type": "int"},
{"name": "source", "type": "string"},
{"name": "sensor", "type": "string"}
]
}
Some more information about some fields that are unique to that schema. The IPs in Authority IP are the collection of the authority name server IPs that replied to our query. We gather all the IPs that gave us the same answer for an entire day and concatenate them on the same field, mostly in order to reduce the number of records that we have to keep. The only field that might be slightly confusing, is the "hours" field. This is a 24bit integer that encodes the time of day we saw this RR for date date (for example, 000000000000000001000010 = 18:00 and 23:00). Another important thing to keep in mind, is NXDOMAINs. A resolved QNAME does not exist when both the rdata and ttl fields are equal to null. If rdata exists but ttl is null then the record was part of the glue of the DNS packet and not in the answer section.
Akamai provides aggregated data about the root servers. They provide the overall amount of DNS queries, trends, and IPv4/IPv6 query ratios.
APNIC gathers many different statistics and offers them on their website. However, they provide way more data then it might initially look like, since many of the datasets are not linked from their main page.
Overview of datasets, monitors, and reports produced and organized by Caida. Also contains links to other datasets.
Censys performs regular scans for common protocols (e.g., DNS, HTTP(S), SSH). Provides a search for TLS certificates.
Access is free, but requires registration.
@InProceedings{censys15,
author = {Zakir Durumeric and David Adrian and Ariana Mirian and Michael Bailey and J. Alex Halderman},
title = {A Search Engine Backed by {I}nternet-Wide Scanning},
booktitle = {Proceedings of the 22nd {ACM} Conference on Computer and Communications Security},
month = oct,
year = 2015
}
Collection of "bad" packets in PCAPs that can be used for testing software.
Provides an outdated list of different Cyber Thread Intelligence Feeds of other organizations.
dn42 is a big dynamic VPN. It employs various Internet technologies, such as BGP, whois, DNS, etc.
Users can experiment with technology, they normally would not use in a separated environment.
Mostly different hackerspaces participate in the dn42 network, such as different locations of the CCC.
Tool to replay DNS queries captured in a pcap file with accurate timing between queries. Allows modifying the replay like changing IP addresses, speed up or slow down the queries.
DNS network capture utility. Similar in concept to tcpdump, but with specialized options for DNS.
DNS performance measurement tools.
This is an improvement on Paris traceroute and the classical traceroute. It can detect changing routes and detect NATs along the path.
Historical dataset about IP to ASN mappings.
Historical dataset about IP to ASN mappings.
Per continent, region, or country measurements of IPv6 deployment and preference. Allows to access historical data.
Per continent, region, or country measurements of IPv6 deployment and preference.
A curated list of IPv6 hosts, gathered by crawling different lists. Includes:
Access to the full list requires registration by email.
Based on the paper "Scanning the IPv6 Internet: Towards a Comprehensive Hitlist".
These projects either operate DNS based Real-time Blackhole Lists (RBL) or allow checking if an IP is contained. The Multi-RBL websites are helpful in finding a large quantaty of RBLs.
Multi-level MDA-Lite Paris Traceroute is a traceroute tool, which understands and learns more complex network topologies. Often times the network is not just a line, but multiple paths are possible and chosen at random.
A good description of the tool can be found in the RIPE Labs post or in the IMC 2018 paper.
This is an improvement on the traditional traceroute program. It is able to detect multiple distinct routes and display them accordingly. The classical traceroute would produce weird results on changing network routes.
Another similar program is Dublin traceroute.
Passive DNS dataset from circl.lu.
RIPE operates a set of probes, which can be used to send pings or similar measurements. The probes are mainly placed in Europe but some are also in other continents.
All the collected measurements can be found in the RIPE Atlas Daily Archives. The blog post gives some more details.
A list of Internet scans for free to download. Some of the data is historical, some scans are still actively updated.
Links to a downloadable list of the Alexa top 1 million.
Shodan performs regular scan on common ports.
Access is free, but requires registration. More results can be gained with a paid account.
A traceroute like tool, that detects where a path crosses an IXP.
These services allow you to create a domain name for any IP address. The IP address is encoded into the domain name. An overview over different services can be found here.
http://xip.io/ provides IPv4 only
10.0.0.1.xip.io resolves to 10.0.0.1www.10.0.0.1.xip.io resolves to 10.0.0.1foo.bar.10.0.0.1.xip.io resolves to 10.0.0.1https://nip.io/ provides IPv4 only
. and - separators.10.0.0.1.nip.io resolves to 10.0.0.1192-168-1-250.nip.io resolves to 192.168.1.250customer1.app.10.0.0.1.nip.io resolves to 10.0.0.1magic-127-0-0-1.nip.io resolves to 127.0.0.1https://sslip.io/ provides IPv4 and IPv6
. and - separators.192.168.0.1.sslip.io resolves to 192.168.0.1192-168-1-250.sslip.io resolves to 192.168.1.250www.192-168-0-1.sslip.io resolves to 192.168.0.1–1.sslip.io resolves to ::12a01-4f8-c17-b8f--2.sslip.io resolves to 2a01:4f8:c17:b8f::2https://ip6.name/ provides IPv6 only
x replaces the :: in the IPv6 address.2001.db8.8000.0.0.0.0.1.ip6.name resolves to 2001:db8:8000::12001.db8.8000.x.1.ip6.name resolves to 2001:db8:8000::1x.1.ip6.name resolves to ::1
Different utilities for network scanning. Most imporantly the zmap component, which is a packet scanner for different protocols. It also contains other tools like ways to iterate over the IPv4 address space and blacklist/whitelist management.