Skip to content

Hostname

dnslify.com

Last fetched

dnslify.com resolves to 104.21.27.161, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. dnslify.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · dnslify.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/dnslify.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1387
Registrant organisation
c/o whoisproxy.com
Contact emails
dnslify.com@superprivacyservice.com, 162a96f631@dnslify.com.whoistrustee.com, 04064a82f78b1c928333b71a024caa9ff5713012d93795c31fde72faf3c45ef4@dnslify.com.whoisproxy.org, 0a02a319a2676c91ab4f2dc9668e0270912bfa0efe5b13beb2e4fbc56839fa04@dnslify.com.whoisproxy.org, 9f0574adf2ae9e78adc607d5ac25fc1f24d5e30d36994a3ff73ad2d9d55b9ad9@dnslify.com.whoisproxy.org, a2ce24c1b8ef01664cfbb1b6253c11cf7187a2c4e5d5d032aed9ad799e41a4ab@dnslify.com.whoisproxy.org, b0bec48f1e5e9450a30250eb1076480d8558b561b7ae19b79dc36a0fabf4ca36@dnslify.com.whoisproxy.org, c772daa1dffc6002d2b0fb6f06c76fa8efff56d618ab1a1e07a9217229735fd6@dnslify.com.whoisproxy.org

Subdomains

Subdomain
api.dnslify.com
chronograf.dnslify.com
doh.dnslify.com
ns.dnslify.com
stats.dnslify.com
www.dnslify.com

Showing 6 of 15. 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.

Sample inbound links

Mail and authentication

Nameservers

  • beau.ns.cloudflare.com
  • kim.ns.cloudflare.com

MX records

  • mx1.peerix.net
  • mx2.peerix.net

Threat-feed evidence

History

Related pages

Pivot from dnslify.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: "dnslify.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.