Skip to content

Hostname

dotupdate.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
373290b126df46318e58984de8aaea8e.protect@withheldforprivacy.com, dnstech@dotinc.net

Subdomains

Subdomain
dcc.dotupdate.com
dev.dotupdate.com
stage.dotupdate.com
staging.dotupdate.com
www.dotupdate.com
www2.dotupdate.com

Showing 6 of 6 subdomains (6 per page).

Mail and authentication

Nameservers

  • ns1.vultr.com
  • ns2.vultr.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

  • mx1.improvmx.com
  • mx2.improvmx.com

SPF policy

  • ip: 159.183.0.0/16
  • ip: 149.72.0.0/16
  • ip: 168.245.0.0/17
  • ip: 167.89.0.0/17
  • ip: 50.31.32.0/19
  • ip: 192.254.112.0/20
  • ip: 198.37.144.0/20
  • ip: 208.117.48.0/20
  • ip: 198.21.0.0/21
  • a: dotupdate.com
  • mx: dotupdate.com
  • include: spf.improvmx.com
  • include: mail.zendesk.com
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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