Skip to content

Hostname

ourdailybears.com

Last fetched

ourdailybears.com resolves to 151.101.1.34, announced in 151.101.0.0/22 by FASTLY - Fastly, Inc. in CA. ourdailybears.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 · ourdailybears.comRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/ourdailybears.com

Resolution chain

IPv6 resolution

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

Attribution

Fastly

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of ourdailybears.com owner
Contact emails
domain.names@voxmedia.com, 5771eef3-e214-4785-a128-8b316fa71ea0@identity-protect.org, 79c07a34-5853-45fe-876d-049531107250@identity-protect.org, a7055ded-be87-4a47-b41c-731d318a726b@identity-protect.org, ba788360-a239-42d0-9427-dcb931b4dca6@identity-protect.org, e34e2b15-0a14-4cce-90f1-3594ac058ce7@identity-protect.org

Subdomains

Subdomain
www.ourdailybears.com

Showing 1 of 1 subdomain (1 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

Mail and authentication

Nameservers

  • ns-474.awsdns-59.com
  • ns-1022.awsdns-63.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-1532.awsdns-63.org
  • ns-1935.awsdns-49.co.uk

MX records

  • mail1.sbnation.com

Threat-feed evidence

History

Related pages

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