Skip to content

Hostname

weekend.com

Last fetched

weekend.com resolves to 104.26.14.236, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. weekend.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 · weekend.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/weekend.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
trivago n.v.
Contact emails
ap9r69m88hy@networksolutionsprivateregistration.com, ay6bt7vp3zm@networksolutionsprivateregistration.com, bm2dj8uq2f7@networksolutionsprivateregistration.com, cs56p3xt9hn@networksolutionsprivateregistration.com, dw9zb6wy6v2@networksolutionsprivateregistration.com, hg7799hv56e@networksolutionsprivateregistration.com, na-domainadmin@travelzoo.com, pr6c234j2mu@networksolutionsprivateregistration.com, c3f6f0cd2bb84533abcb9500e61f58d6.protect@withheldforprivacy.com, ralphb@travelzoo.com, sj8q39c5887@networksolutionsprivateregistration.com, ts42h66v85g@networksolutionsprivateregistration.com, domainadmin@trivago.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

  • sid.ns.cloudflare.com
  • sunny.ns.cloudflare.com
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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