Skip to content

Hostname

dicelaboratory.com

Last fetched

dicelaboratory.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. dicelaboratory.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 · dicelaboratory.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/dicelaboratory.com

Resolution chain

No IPv4 resolution is recorded for dicelaboratory.com in WhisperGraph.

IPv6 resolution

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

WHOIS identity

Registrar
iana:468
Contact emails
362af8f5-5eec-469f-ac3c-9013c2502483@identity-protect.org, 3c2029ae-ae7f-4dcf-987b-0d00be30a5e1@identity-protect.org, 576aefe8-9153-459c-a7d9-c7f31287096e@identity-protect.org, 77265c83-89c4-40db-9880-c9783d89d896@identity-protect.org, 7ee0cacf-af23-4100-aecf-4359f4ca789a@identity-protect.org, 9f89d861-d9d8-454d-8b17-df7ce1c20936@identity-protect.org, a297b610-af0d-4d50-af89-92e4554638e4@identity-protect.org, owner-10819650@dicelaboratory.com.whoisprivacyservice.org, owner-169671@dicelaboratory.com.whoisprivacyservice.org, owner-2245714@dicelaboratory.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-173.awsdns-21.com
  • ns-663.awsdns-18.net
  • 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
  • ns-1412.awsdns-48.org
  • ns-1693.awsdns-19.co.uk

Threat-feed evidence

History

Related pages

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