Skip to content

Hostname

clockworksms.com

Last fetched

clockworksms.com resolves to 54.72.194.82, announced in 54.72.0.0/16 by AMAZON-02 - Amazon.com, Inc. in IE. clockworksms.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 · clockworksms.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/clockworksms.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1052
Registrant organisation
allan england
Contact emails
uk.technicalservices.team@commify.com, allan@mediaburst.co.uk, mediaburst@martinsteel.co.uk

Subdomains

Subdomain
api.clockworksms.com
api3.clockworksms.com
api5.clockworksms.com
app.clockworksms.com
app3.clockworksms.com
app5.clockworksms.com
docs.clockworksms.com
www.clockworksms.com

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

  • ns1.eurodns.com
  • ns2.eurodns.com
  • ns3.eurodns.com
  • ns4.eurodns.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

  • mail.mediaburst.net
  • mail.mediaburst.org.uk

SPF policy

  • mx: clockworksms.com
  • include: cmail1.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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