Skip to content

Hostname

changingworkplace.com

Last fetched

changingworkplace.com resolves to 217.20.16.142, announced in 217.20.16.0/20 by DATAHOP - Six Degrees Technology Group Limited in GB. changingworkplace.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 · changingworkplace.comRouting diversity1.5/10Peering density5.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint7.2/10canon.whisper.security/host/changingworkplace.com

Resolution chain

IPv6 resolution

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

Attribution

six degrees group

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
steve thorley
Contact emails
it-infrastructure@changingworkplace.com, a19fadf238308173b693a85599415f8f-3891569@contact.gandi.net

Subdomains

Subdomain
cdn.changingworkplace.com
email.changingworkplace.com
rdp.changingworkplace.com
rds.changingworkplace.com
www.changingworkplace.com

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

  • ns-9.awsdns-01.com
  • ns-942.awsdns-53.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • f.root-servers.net
  • h.root-servers.net
  • k.root-servers.net
  • m.root-servers.net
  • ns-1188.awsdns-20.org
  • ns-1862.awsdns-40.co.uk

MX records

  • changingworkplace-com.mail.protection.outlook.com

SPF policy

  • ip: 217.20.16.128/27
  • ip: 191.237.89.245/32
  • include: emsd1.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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