Skip to content

Hostname

shingle.com

Last fetched

shingle.com resolves to 3.15.118.250, announced in 3.14.0.0/15 by AMAZON-02 - Amazon.com, Inc. in US. shingle.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 · shingle.comRouting diversity2.4/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/shingle.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
bs2k28nm2rp@networksolutionsprivateregistration.com, ep8mk4ku3sm@networksolutionsprivateregistration.com, pq8km6c93bx@networksolutionsprivateregistration.com, rp25m5vc8r6@networksolutionsprivateregistration.com, ym4746mr3kg@networksolutionsprivateregistration.com, support@beringer.net, teamsupport@beringer.net

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

  • ns100.worldnic.com
  • ns99.worldnic.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

  • mxa-00317901.gslb.pphosted.com
  • mxb-00317901.gslb.pphosted.com

SPF policy

  • ip: 205.173.226.5/32
  • a: aushossmtpprd01.activant.com
  • include: customers.clickdimensions.com
  • include: spf.protection.outlook.com
  • include: %{ir}.%{v}.%{d}.spf.has.pphosted.com
  • include: spf-00317901.pphosted.com
  • include: spf.exclaimer.net

Threat-feed evidence

History

Related pages

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