Skip to content

Hostname

precisiondoordelaware.com

Last fetched

precisiondoordelaware.com resolves to 23.33.42.133, announced in 23.33.42.0/24 by AKAMAI-ASN1 - Akamai International B.V. in US. precisiondoordelaware.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 · precisiondoordelaware.comRouting diversity2.4/10Peering density8.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/precisiondoordelaware.com

Resolution chain

IPv6 resolution

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

Attribution

akamai international

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
brian kruger
Contact emails
briankruger@forissolutions.com, marketing@forissolutions.com

Subdomains

Subdomain
dev.precisiondoordelaware.com
refer.precisiondoordelaware.com
snippet.precisiondoordelaware.com
www.precisiondoordelaware.com

Showing 4 of 4 subdomains (4 per page).

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

Sample outbound links

Mail and authentication

Nameservers

  • a1-13.akam.net
  • a10-66.akam.net
  • a20-67.akam.net
  • a22-64.akam.net
  • a5-65.akam.net
  • a7-66.akam.net

MX records

  • precisiondoordelaware-com.mail.protection.outlook.com

SPF policy

  • include: spf.ess.barracudanetworks.com
  • include: spf.protection.outlook.com
  • a: precisiondoordelaware.com
  • mx: precisiondoordelaware.com
  • include: spf.us.emailservice.io
  • include: sendgrid.net
  • ip: 198.37.150.8
  • ip: 69.167.169.178

Threat-feed evidence

History

Related pages

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