Hostname
redtractor.org.uk
Last fetched
redtractor.org.uk resolves to 1 IPv4 address operated by GOOGLE-CLOUD-PLATFORM - Google LLC in US. WHOIS lists registrar:123-reg limited t/a 123-reg [tag = 123-reg] as the registrar.
Nutrition Label
Resolution chain
redtractor.org.uk resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.196.130.104 | 104.196.128.0/20 | AS396982 | GOOGLE-CLOUD-PLATFORM - Google LLC | US |
WHOIS identity
- Registrar
- registrar:123-reg limited t/a 123-reg [tag = 123-reg]
- Organization
- assured food standards
- Contact emails
- —
Subdomains
24 observed subdomains of redtractor.org.uk.
Showing 23 of 24. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from redtractor.org.uk in the public web crawl.
470 sites link to this hostname.
164 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
15 SPF mechanisms authorising senders for redtractor.org.uk.
| Mechanism | Target |
|---|---|
| SPF_A | id42398.everysite.co.uk |
| SPF_INCLUDE | _spf.intacct.com |
| SPF_INCLUDE | gbr.pb-dynmktge.com |
| SPF_INCLUDE | relay.mailchannels.net |
| SPF_INCLUDE | servers.mcsv.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 217.33.230.106 |
| SPF_IP | 77.72.202.120 |
| SPF_IP | 81.93.164.103/32 |
| SPF_IP | 81.93.173.201/32 |
| SPF_IP | 83.170.89.31 |
| SPF_IP | 83.170.98.129 |
| SPF_IP | 87.230.62.203 |
| SPF_IP | 88.202.186.185 |
| SPF_IP | 88.202.188.141/32 |
Related pages
Pivot deeper into the graph from redtractor.org.uk.
- IP · 104.196.130.104
- ASN · AS396982GOOGLE-CLOUD-PLATFORM - Google LLC
- Registrar · registrar:123-reg limited t/a 123-reg [tag = 123-reg]
- Country · US
- Apex domain · org.uk
- TLD · .uk
- Browse hostnames · re…
- 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: "redtractor.org.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.