Hostname
wirefence.co.uk
Last fetched
wirefence.co.uk resolves to 4 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists registrar:123-reg limited t/a 123-reg [tag = 123-reg] as the registrar.
Nutrition Label
Resolution chain
wirefence.co.uk resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.75.157 | 104.21.64.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.178.111 | 172.67.176.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.96.3 | 188.114.96.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 188.114.97.3 | 188.114.97.0/24 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- registrar:123-reg limited t/a 123-reg [tag = 123-reg]
- Organization
- —
- Contact emails
- —
Subdomains
1 observed subdomain of wirefence.co.uk.
| Subdomain |
|---|
| www.wirefence.co.uk |
Web-graph footprint
Distinct hostnames that link to or from wirefence.co.uk in the public web crawl.
216 sites link to this hostname.
645 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
8 SPF mechanisms authorising senders for wirefence.co.uk.
| Mechanism | Target |
|---|---|
| SPF_A | jensen.aira.net |
| SPF_A | wirefence.co.uk |
| SPF_INCLUDE | _spf.google.com |
| SPF_INCLUDE | _spf.mlsend.com |
| SPF_INCLUDE | relay.kinstamailservice.com |
| SPF_INCLUDE | sendgrid.net |
| SPF_IP | 212.113.133.144 |
| SPF_MX | wirefence.co.uk |
Related pages
Pivot deeper into the graph from wirefence.co.uk.
- IP · 104.21.75.157
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · registrar:123-reg limited t/a 123-reg [tag = 123-reg]
- Country · CA
- Apex domain · co.uk
- TLD · .uk
- Browse hostnames · wi…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "wirefence.co.uk"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.