Skip to content

Hostname

timely.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
domains by proxy,
Contact emails
timely.com@domainsbyproxy.com, 94e4f86f63bf47d3a78e583a19efe175.protect@whoisguard.com, 01b5a021067248e58a2d260fc00357fc.protect@withheldforprivacy.com, 35269600ddea4baf87317fe029c1c5f7.protect@withheldforprivacy.com, de748e17f61f400cbd17067469f2e2f9.protect@withheldforprivacy.com

Subdomains

Subdomain
comdash.timely.com
dewo.timely.com
go.timely.com
hub.timely.com
ims.timely.com
www.timely.com

Showing 6 of 6 subdomains (6 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

  • elaine.ns.cloudflare.com
  • matt.ns.cloudflare.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

  • smtp.google.com

SPF policy

  • include: _spf.google.com
  • include: spf.mail.intercom.io
  • include: 3431737.spf01.hubspotemail.net
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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