Skip to content

Hostname

digiflazz.com

Last fetched

digiflazz.com resolves to 18.136.89.82, announced in 18.136.0.0/16 by AMAZON-02 - Amazon.com, Inc. in SG. digiflazz.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 · digiflazz.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/digiflazz.com

Resolution chain

IPv6 resolution

No AAAA record for digiflazz.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of digiflazz.com owner
Contact emails
digiflazz.com@protecteddomainservices.com, 173edf57-8b20-49ad-9350-9a679b2fdca1@identity-protect.org, 65d21c12-73ae-43dd-920b-e1ecaaa129cb@identity-protect.org, 71321ea2-ae3d-4903-a1bf-fc63a46869ac@identity-protect.org, 899b871b-a96f-4cfc-9b75-59c3079775ef@identity-protect.org, a6f8b1f6-675f-4a20-b95c-daaa2402f6ba@identity-protect.org, aaf6c955-390d-4c58-8f09-29433b85147e@identity-protect.org, d4df412d-4525-4cf6-8a48-a120349b8243@identity-protect.org, owner-6917707@digiflazz.com.whoisprivacyservice.org

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

  • ns-110.awsdns-13.com
  • ns-614.awsdns-12.net
  • ns-1134.awsdns-13.org
  • ns-1813.awsdns-34.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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