Technology
Document Type Definition
Last fetched
Document Type Definition is a technology in WhisperGraph's PredictLeads-derived TECHNOLOGY corpus, categorized under documentation tools, with a published adopter count of 51 hostnames.
Profile
- Category
- documentation tools
- Broader grouping
- web tools and plugins, software development
- Published adopter count
- 51
- Vendor
- w3.org
Document Type Definition (DTD) is a schema language used to define the structure and rules for XML documents. It specifies allowed elements, attributes, and their relationships, ensuring data consistency and validity. DTDs can be declared internally within an XML file or referenced externally. They are commonly used in data exchange, configuration files, and systems requiring strict document formatting and validation.
Vendor site: https://www.w3.org/TR/REC-xml/#dt-doctype
Sample adopters
20 hostnames WhisperGraph observed running Document Type Definition, a sample of the 51 published adopters.
Hosting concentration
The networks announcing the IP addresses of a sample of 20 Document Type Definition adopters, not of all 51 published adopters. A hostname counts once per network.
- AS133353 of 20 sampled
- AS165092 of 20 sampled
- AS195512 of 20 sampled
- AS45832 of 20 sampled
- AS146181 of 20 sampled
- AS185631 of 20 sampled
- AS2092421 of 20 sampled
- AS263421 of 20 sampled
- AS263471 of 20 sampled
- AS35731 of 20 sampled
- AS3981011 of 20 sampled
- AS3987871 of 20 sampled
- AS475831 of 20 sampled
- AS541131 of 20 sampled
- AS80751 of 20 sampled
Related pages
Pivot from Document Type Definition into its category and the vendor behind it.
Queries
Resolves the slug's technology-name candidate(s) and projects the winner's fields.
MATCH (t:TECHNOLOGY)
WHERE t.name =~ $pattern
WITH t ORDER BY t.adopterCount DESC, t.name ASC
WITH collect(t)[0] AS winner, count(t) AS candidates
RETURN winner.name AS name,
winner.description AS description,
winner.category AS category,
winner.parentCategories AS parentCategories,
winner.adopterCount AS adopterCount,
winner.url AS url,
winner.vendorApex AS vendorApex,
candidatesRun yourself →Reads a 20-host adopter sample and the ASNs announcing its IP addresses.
MATCH (:TECHNOLOGY {name: $name})<-[:RUNS_TECHNOLOGY]-(h:HOSTNAME)
WITH h LIMIT 20
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
RETURN h.name AS host, a.name AS asn
LIMIT 200Run yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.