Skip to content

Hostname

wolseley.com

Last fetched

wolseley.com resolves to 13.248.160.137, announced in 13.248.160.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. wolseley.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 · wolseley.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/wolseley.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:269
Registrant organisation
domain admin
Contact emails
wolseley.com+registrant@customer.demys.com, gtld@demys.com, info@domain-contact.org

Subdomains

Subdomain
access.wolseley.com
accesslmt.wolseley.com
citrixna.wolseley.com
citrixnaleb.wolseley.com
citrixnalebtest.wolseley.com
citrixnanpn.wolseley.com
citrixnanpntest.wolseley.com
citrixnatest.wolseley.com
desktopna.wolseley.com
dev-xmatters.wolseley.com
ds.wolseley.com
esb.wolseley.com

Showing 12 of 67. 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

  • ns1.redacteddns.com
  • ns2.redacteddns.com
  • ns3.redacteddns.com
  • ns4.redacteddns.com
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
  • dns4.p05.nsone.net

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com
  • wolseley-com.mail.protection.outlook.com

SPF policy

  • include: %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email

Threat-feed evidence

History

Related pages

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