Skip to content

Hostname

logistics.org.uk

Last fetched

logistics.org.uk resolves to 104.20.38.145, announced in 104.20.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. logistics.org.uk 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 · logistics.org.ukRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/logistics.org.uk

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:virgin media business ltd [tag = virginmedia]
Registrant organisation
stung

Subdomains

Subdomain
connect.logistics.org.uk
consortium.logistics.org.uk
devmiap.logistics.org.uk
devnewselfadmin.logistics.org.uk
devnewvision.logistics.org.uk
devpcnadmin.logistics.org.uk
devselfadmin.logistics.org.uk
devtms.logistics.org.uk
devvia.logistics.org.uk
devvision.logistics.org.uk
devvisionadmin.logistics.org.uk
devvisionmemberadmin.logistics.org.uk

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

Mail and authentication

Nameservers

  • priscilla.ns.cloudflare.com
  • sid.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

  • eu-smtp-inbound-1.mimecast.com
  • eu-smtp-inbound-2.mimecast.com

SPF policy

  • redirect: _s3v8n6nmr.sdmarc.net

Threat-feed evidence

History

Related pages

Pivot from logistics.org.uk 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: "logistics.org.uk"})-[: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.