Skip to content

Hostname

smashburger.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:470
Registrant organisation
dasha landry
Contact emails
dlandry@smashburger.com, smashburger.com-registrant@anonymised.email, domadmin@jollibee.com.ph

Subdomains

Subdomain
abcreports.smashburger.com
abreports.smashburger.com
autodiscover.smashburger.com
clicks.smashburger.com
cms.smashburger.com
coresitefw01.smashburger.com
dam.smashburger.com
dev.smashburger.com
e.smashburger.com
locations.smashburger.com
locationtest.smashburger.com
mobile.smashburger.com

Showing 12 of 24. View all subdomains →

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

  • dom.ns.cloudflare.com
  • gail.ns.cloudflare.com

MX records

  • smashburger-com.mail.protection.outlook.com
  • mxa-0027d001.gslb.pphosted.com
  • mxb-0027d001.gslb.pphosted.com

SPF policy

  • ip: 209.143.138.192/27
  • ip: 68.71.86.32/27
  • include: amazonses.com
  • include: spfa.cpmails.com
  • include: spf.protection.outlook.com
  • include: spf-0027d001.pphosted.com
  • include: spf.pxsmail.com
  • include: mail.zendesk.com
  • ip: 34.225.202.6

Threat-feed evidence

History

Related pages

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