Hostname
kms-technology.com
Last fetched
kms-technology.com resolves to 104.20.16.82, announced in 104.20.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. kms-technology.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.20.16.82
104.20.16.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.159.234
172.66.144.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for kms-technology.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1649
- Registrant organisation
- domain admin
- Contact emails
- tech@kms-technology.com, protected@domainwhoisprotect.net
Subdomains
Showing 12 of 54. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns1.kms-technology.com
- ns2.kms-technology.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.alchemer.com
- include: _spf.google.com
- include: spf.mandrillapp.com
- include: 4508000.spf04.hubspotemail.net
- include: servers.mcsv.net
- ip: 115.84.182.104
Threat-feed evidence
History
Related pages
Pivot from kms-technology.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "kms-technology.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.